-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add check_tbl_derived_task_id_vals()
function
#176
Conversation
…s are valid. Resolves #110
file_path = "flu-base/2022-10-22-flu-base.csv", | ||
skip_submit_window_check = TRUE | ||
) | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this because of the introduction of the new check, now when derived_task_ids
are NULL the check is skipped and a message returned whereas if derived_task_ids
are included, the result of the check is retuned. Hence these two situations do not return the same result anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me! There are two simplifications to the code that I suggested.
Thanks @zkamvar ! Feel free to push forward with suggestions and merge |
This PR adds the
check_tbl_derived_task_id_vals()
check tovalidate_model_data()
that ensures that values in derived task ID columns match expected values for the corresponding derived task IDs in the round as defined intasks.json
config Given the dependence of derived task IDs on the values of other values, the check ignores the combinations of derived task ID values with those of other task IDs and focuses only on identifying values that do not match corresponding accepted values. This ensuresderived_task_ids
values which are ignored in all other standard value checks receive atl east some basic validation.Resolves #110